Summary

Regenerates the SDK from the latest OpenAPI spec and wires the new
rebuild-schedule operation into the hand-rolled LedgerClient facade.
Without the facade method the regenerated operation would ship but be
unreachable through LedgerClient.

Changes

SDK regeneration (chore(sdk) commit)

• New operation surface for rebuild-schedule: api/extensions_robo_ledger/op_rebuild_schedule.py, RebuildScheduleRequest, ScheduleCreatedResponse (+ ScheduleCreatedResponseRuleSummaryType0), and the OperationEnvelopeScheduleCreatedResponse wrapper, all re-exported from models/__init__.py.
• Docstring refresh in update_schedule_arm.py / update_schedule_request.py: the "create a fresh schedule" pointer now references create-information-block (block_type='schedule') instead of the old create-schedule. No facade change needed there — create_schedule() already routes through op_create_information_block.

Facade (feat(ledger) commit)

• LedgerClient.rebuild_schedule(graph_id, structure_id, *, idempotency_key=None) in the Schedules section. Re-runs the schedule generator in place on an existing schedule — preserves the structure id, element associations, and taxonomy while voiding the old obligation chain and regenerating facts + a fresh obligation chain. Threads the optional Idempotency-Key header and returns ScheduleCreatedResponse via the existing typed-envelope unwrap helpers.
• Two tests in TestScheduleAdditionalOps: basic call (asserts result, graph_id, request body, and idempotency_key is UNSET) and idempotency-key passthrough.

Testing

• pytest tests/test_ledger_client.py — 91 passed.
• Full suite ran via the pre-commit hook on both commits — 439 passed, 17 skipped.
• ruff check on the edited files — clean.

Notes

• The TypeScript client has no hand-rolled facade (fully generated), so no parallel change is required there.